Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client/rpc: migrate go-ipfs-http-client #9906

Merged
merged 130 commits into from
May 31, 2023
Merged

client/rpc: migrate go-ipfs-http-client #9906

merged 130 commits into from
May 31, 2023

Conversation

Jorropo
Copy link
Contributor

@Jorropo Jorropo commented May 30, 2023

Updates #9124

This commit was moved from ipfs/go-ipfs-http-client@4e7edce
This commit was moved from ipfs/go-ipfs-http-client@e06cddb
This commit was moved from ipfs/go-ipfs-http-client@a23d794
This commit was moved from ipfs/go-ipfs-http-client@d0c98b8
This commit was moved from ipfs/go-ipfs-http-client@3217104
This commit was moved from ipfs/go-ipfs-http-client@60321ed
This commit was moved from ipfs/go-ipfs-http-client@5b2c99a
lidel and others added 8 commits June 23, 2022 22:39
This ensures cid-codec introduced in #8568
gets correctly passed (+ we maintain backward-compatibility with CIDv0)

This commit was moved from ipfs/go-ipfs-http-client@9c9f43f
Currently any clients created through `NewApiWithClient` will make a
HTTP request to the api, even if the multiaddress specifies TLS or (the
deprecated multiaddr option) https.

This commit addresses this by having NewApiWithClient iterate the
available protocols for the multiaddress, specifying the URL proto as
https if it finds TLS or HTTPS is specified. The default continues to be
http for those multiaddresses that do not specify these options.

Should resolve #176

This commit was moved from ipfs/go-ipfs-http-client@7e1de1f
@Jorropo Jorropo requested a review from a team as a code owner May 30, 2023 17:06
@Jorropo Jorropo changed the title Go ipfs http client client/rpc: migrate go-ipfs-http-client May 30, 2023
@Jorropo Jorropo force-pushed the go-ipfs-http-client branch 2 times, most recently from 2c07825 to ccbae53 Compare May 30, 2023 17:24
@Jorropo Jorropo force-pushed the go-ipfs-http-client branch 5 times, most recently from 46feec1 to f1e4a15 Compare May 30, 2023 19:20
@Jorropo
Copy link
Contributor Author

Jorropo commented May 30, 2023

Note this needs a merge with merge not rebase nor squash.

@@ -4,5 +4,8 @@ linters:

linters-settings:
stylecheck:
checks:
- all
- '-ST1003'
Copy link
Member

@hacdias hacdias May 31, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with skipping this for now to avoid breaking people migrating, but the rule is indeed correct: https://github.com/golang/go/wiki/CodeReviewComments#initialisms

@hacdias hacdias merged commit 4019d94 into master May 31, 2023
@hacdias hacdias deleted the go-ipfs-http-client branch May 31, 2023 08:17
http-client, making it impossible to use them together with the same coreapi
version.

**TODO(@Jorropo)**: add link to `boxo-migrate` once support for rewriting this import path has been added
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FYSA: I merged this PR assuming this will be updated before the release with the correct instructions. Feel free to ping me to review that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

Successfully merging this pull request may close these issues.